5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
- Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-3: Specifying Statements

The Application ID


The application ID component identifies the application that a specified file or field is associated with. This allows you, for example, to compare the value of a field in one application to that of a field in a second application. All the statement types that allow you to specify files or fields require you to provide the corresponding application ID. Note that, when you refer to any of the predefined fields (PDFs) in a statement, you enter '---' (three hyphens) as the application ID. When you specify a constant (such as when adding the value 3 to a designated numeric field), you leave the application ID as spaces. The following is an example of an application ID reference:

   TFT    READ TAR RECEIPT1   HOLD 0 FT 0 BY RECEIPT1 KEY

The component TAR refers to the application ID in which the RECEIPT1 file is defined.

When you are entering new ILF code with an application ID component, the application ID defaults to the current application but you can override it. APPX automatically changes the application ID to "---" if the referenced field (or file or process) cannot be found in the application specified but does exist in application 0LA, the runtime application. This lets you refer to predefined fields, files, or processes without having to change the application ID.

Application Design Manual                                         "Powered by Appx Software"

540

©2006 By APPX Software, Inc. All Rights Reserved